Problem

Based on the Reliability Epic, we want:

As a developer, I want a simple API to register hooks to process messages on one or several content topics

This also ties in with #2022, where Filter API is hard-to-understand, and involves multiple steps:

const { error, subscription } = await node.filter.createSubscription(shardInfoOrPubsubTopic);
const results = await subscription.subscribe([decoder], callback);

Solution

Based on the fact that decoder has information about the pubsubTopic as well as contentTopic, we can use decoders to fetch information about both the topics, and API can be condenses into:

const { error, subscription, results } = await node.filter.subscribe([decoder], callback);

Notes

• Resolves https://github.com/orgs/waku-org/projects/2/views/1?pane=issue&itemId=66219817
• Related to [Epic: js-waku] Reliability Protocol for Resource-Restricted Clients #2154
• This PR also resolves feat: remove filter.subscribe() dependency on IReceiver #1979, where IReceiver dependency is renamed to subscribeWithFilter instead, and subscribe() is brought out as the primary API (feat: remove filter.subscribe() dependency on IReceiver #1979 (comment))
• updates tests

Contribution checklist:

• covered by unit tests;
• covered by e2e test;
• add ! in title if breaks public API;